Introduction

As part of our regular Quality Assurance control, the IBM® Sametime® United Telephony (SUT) Systems Verification Test (SVT) team executes reliability tests on SUT environments. This article describes the process used internally within IBM to generate test users for reliability test cases.

We describe how to provision 15,000 users for a SUT workload. These users need to be created in the LDAP after which the IBM Tivoli® Directory Integrator (TDI) process is used to generate importFiles which are used in the SUT Common Management Portal (CMP) console.

Adding users in LDAP

Generate users DN

For this example we are using Tivoli Directory Server 6.2 as our LDAP server.

1. First, we need to create the base DN (domain name) where users' data will be stored; in this case, the ldif file 852_819OC_DN.ldif was created (see figure 1).

Figure 1. ldif file with users' DN



2. Use the following command to generate a DN:
3. Look for the following log messages to confirm that the import operation completed successfully:
The LDAP GUI reflects that new records were created (see figure 2).

Figure 2. Users' DN in LDAP GUI

Generating ldif file with users' details

1. Using your preferred tool/script, create an ldif file similar to the one illustrated below (with 15,000 users); entries should be of the format:
2. When the file is ready, execute the following command to begin the import:
This can also be confirmed in the LDAP GUI (see figure 3).

Figure 3. LDAP users created

Create a group

The next step is to create a group in the LDAP:

1. First prepare the ldif file as shown in the example in figure 4.

Figure 4. Sample ldif for group creation


2. When the file is ready, execute the following command for the import:
Figure 5 shows the group created in the LDAP GUI.

Figure 5. Group in LDAP GUI

Confirm users in the IBM Sametime Connect client

We should now be able to log in to the IBM Sametime Connect client using one of the imported users, as shown in figure 6.

Figure 6. User logged in to Lotus Sametime Connect



We are ready now to provision SUT subscribers.

Adding subscribers with the TDI

Installing TDI

First, we need to install TDI and the provisioning project. If the Telephony Application Server (TAS) has been installed using the ./install.sh all command, then all required files are already installed since the All option includes the TDI and the provisioning project assembly lines.

If TDI is not installed in the TAS server then use the following command:

Prepare setting.xml

Update the setting.xml file, located in cd /opt/IBM/tivoli/tdi/solutions/SUT/, renaming the first template file:
Figure 7 shows and example of a setting.xml file configured to provision TAS users using previously created LDAP records.

Figure 7. Sample setting.xml file


In the above file, we use addCFWD_2.js. It's a simple script:

Initial provisioning process

Now we are ready to run the initial provisioning process, which will create an output CSV file of subscriber data:
As a result, the file output/GrouptestUsers819.csv is generated, to be used in the CMP.

NOTE: Before starting the user provisioning process, the setting.xml file must be prepared, which can be a time-consuming task that you may wish to run in batches. Each execution of the provisioning process retrieves user information from a data source.

The number of retrieved users can be changed in the config/SUTParameters.properties file by changing the value of the UserFetchLimit parameter. It's strongly recommended to set this param to some small number while testing settings in the setting.xml file.

For more details on this process, refer to the product documentation topic, “Adding subscribers with the Tivoli Directory Integrator.”

Changing CMP before importing

Before we start importing the CSV file, we need to make some changes in the CMP.

Add local office code
To do this:

1. Log in to CMP as Administrator.
2. Navigate to Telephony Control Server --- Global Translation and Routing --- Directory Numbers --- Office Codes.
3. Add a new Local Office Code, as shown in figure 8.

Figure 8. Add Office Code window



Define new Destination Code
To do this:

1. In the CMP navigate to Telephony Control Server --- Business Group --- Translation --- Destination Codes.
2. Add the Destination Code as shown in figure 9.

Figure 9. Add destination code

Import users

CSV file generated in previous step can be imported in CMP:

1. In CMP, navigate to Operation & Maintenance --- Recovery --- Import & Export --- Import (see figure 10).

Figure 10. Import function in CMP



2. Select a file to import; click Next (see figure 11).

Figure 11. Import – Step 1 window



3. The next window displays a warning message; this is the default message when provisioning more than 1000 users into the system.

Figure 12. Warning window when importing over 1000 users



Figure 13. Latest Job Status window



4. Per the warning message, after import is completed, restart the system.

Test SUT functionality in Sametime Connect client

The SUT functionality should now be available in the IBM Sametime Connect client, as shown in figure 14.

Figure 14. SUT devices available in Sametime Connect


Test a two-way call, as shown in figure 15.

Figure 15. Calling another user in Sametime Connect


Figure 16 shows that the two-way call was successful.

Figure 16. Successful two-way call



NOTE: The SUT Client is installed automatically with any Sametime Connect client. However, the SUT client plug-ins remain hidden until the administrator adds the user as a SUT subscriber and the enableSUT preference is set to true in the plugin_customization.ini file (installed with the client):

Conclusion

Having read this article you should now have a better understanding of how to:

• Generate a ldif file containing your SUT subscribers.
• Create a SUT subscriber group.
• Install the required TDI with your TAS server and provision users from your LDAP records.
• Make configuration changes to the Office Codes, Local Office Code for the imported users.
• Import users from a CSV file in the CMP.
• Test that the imported users have been provisioned correctly in the Sametime Connect client.

Resources

• Refer to IBM Lotus Sametime family of products, including Lotus Sametime Unified Telephony software.

• Refer to the developerWorks IBM Sametime product page.

About the authors

Tom Ohle and Tomasz Gawlik are experienced Software Engineers working with the System Verification Test Sametime team at IBM's Dublin, Ireland, facility where they specialize in environment configurations, performance, reliability, and stress and load testing. You can reach them at OHLE@ie.ibm.com and TOMGAW@ie.ibm.com.